Description

Fixes native module discovery for Expo and New Architecture (Fabric/TurboModules) consumers. Three issues prevented the SDK from working in expo run:android / expo run:ios projects:

1. Android: GooglePayModule and NetworkingModule were never registered in BoltReactNativeSdkPackage, so TurboModuleRegistry.get() returned null. Both are legacy (ReactContextBaseJavaModule) modules
   and are now registered with isTurboModule = false so bridge interop resolves them correctly.
2. iOS: BoltApplePayButton was missing from the codegen-generated RCTThirdPartyComponentsProvider, causing an "unimplemented component" error at runtime. Added ios.componentProvider to codegenConfig
   in package.json to register it. Also added RCT_EXTERN_MODULE Objective-C bridge files for the BoltApplePay and BoltNetworking Swift modules.
3. Cross-platform: Added platform-specific stubs (NativeApplePayButton.android.ts, NativeGooglePayButton.ios.ts) so codegenNativeComponent is never called for a component that doesn't exist on the
   current platform.

Testing

• Verified on Android emulator: TurboModuleRegistry.get('BoltGooglePay') → true, TurboModuleRegistry.get('BoltNetworking') → true, TurboModuleRegistry.get('BoltApplePay') → false (expected).
• Verified on iOS simulator: TurboModuleRegistry.get('BoltApplePay') → true, TurboModuleRegistry.get('BoltNetworking') → true, TurboModuleRegistry.get('BoltGooglePay') → false (expected).
• Confirmed RCTThirdPartyComponentsProvider.mm now includes BoltApplePayButton → ApplePayButtonComponentView after pod install.
• yarn typecheck, yarn test (115 tests pass), both yarn example ios and yarn example android build and launch successfully.
• Merchant testing: have the reporting merchant rebuild with this version to confirm the "Could not find component config" and "unimplemented component" errors are resolved.

Security Review

• I have considered and reviewed security implications of this PR and included the summary below.

Security Impact Summary

No security-sensitive changes. This PR only fixes native module registration and Fabric component discovery. It does not touch authentication, authorization, payment flows, user data handling, or external
integrations.